Related Changes: Additionally add black dot based on state It used to be the case that the (!info.hasChangeNumber() || !info.hasRevisionNumber())) triggered on merged or abandoned changes. This is not the case any more for all merged and abandoned changes, so we need to transport depend on the state of the change directly to also mark those changes, not covered by the condition as above. Change-Id: I08f97c844d8981a3b400705108e494570d25fc78
diff --git a/Documentation/user-review-ui.txt b/Documentation/user-review-ui.txt index 76220e0..ec9f408 100644 --- a/Documentation/user-review-ui.txt +++ b/Documentation/user-review-ui.txt
@@ -536,12 +536,13 @@ ** [[closed-ancestor]]Black Dot: + -Indicates a merged ancestor, e.g. the commit was directly pushed into +Indicates a closed ancestor, e.g. the commit was directly pushed into the repository bypassing code review, or the ancestor change was reviewed and submitted on another branch. The latter may indicate that the user has accidentally pushed the commit to the wrong branch, e.g. the commit was done on `branch-a`, but was then pushed to `refs/for/branch-b`. +A black dot is also present if the change was abandoned. + image::images/user-review-ui-change-screen-related-changes-indicators.png[width=800, link="images/user-review-ui-change-screen-related-changes-indicators.png"]
